- Replace cuda-core[test] with {include-group = "test"} in cuda-core's
  test-cu* dependency groups. The self-reference triggered setuptools_scm
  via the build backend in CI containers without full git context.
- Pass VCToolsInstallDir through CIBW_ENVIRONMENT_PASS_WINDOWS and
  prepend its bin dir to PATH so MSVC's link.exe is found instead of
  Git's /usr/bin/link.exe when DISTUTILS_USE_SDK=1 skips vcvarsall.bat.
- Regenerate uv.lock.

Co-authored-by: Cursor <cursoragent@cursor.com>

The $VCToolsInstallDir PATH prepend via CIBW_ENVIRONMENT_WINDOWS did
not take effect. Instead, rename Git's /usr/bin/link.exe (POSIX
hardlink tool) before each cibuildwheel build so MSVC's linker is
found on PATH when DISTUTILS_USE_SDK=1 skips vcvarsall.bat.

Co-authored-by: Cursor <cursoragent@cursor.com>

Use ${{ env.VCToolsInstallDir }} (resolved at YAML parse time) instead
of $VCToolsInstallDir (cibuildwheel runtime expansion, which silently
failed). This prepends the MSVC bin dir to PATH so link.exe resolves
to MSVC's linker instead of Git's /usr/bin/link.exe.

Co-authored-by: Cursor <cursoragent@cursor.com>

CIBW_ENVIRONMENT_WINDOWS PATH modifications were not being applied
to the build subprocess. Instead, prepend the MSVC bin dir to PATH
via GITHUB_PATH in the same step that sets DISTUTILS_USE_SDK=1, so
it is inherited by all subsequent steps including cibuildwheel.

Co-authored-by: Cursor <cursoragent@cursor.com>

GITHUB_PATH prepend fixed cibuildwheel but not the Cython test build
step which runs in a different venv context. Rename Git's
/usr/bin/link.exe at the start of the job so MSVC's linker is found
in all steps regardless of PATH ordering.

Co-authored-by: Cursor <cursoragent@cursor.com>

…-workspace

Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.github/workflows/coverage.yml
#	cuda_core/pyproject.toml

cibuildwheel v3.3.x has a PATH mangling bug on Windows that causes
Git's /usr/bin/link.exe to shadow MSVC's linker (pypa/cibuildwheel#2663).
The fix (pypa/cibuildwheel#2723) is merged but not yet released.

Downgrade to v3.2.1 which does not have the bug, removing all the
workarounds: DISTUTILS_USE_SDK=1, CIBW_ENVIRONMENT_PASS_WINDOWS for
MSVC vars, and the link.exe rename hack.

Co-authored-by: Cursor <cursoragent@cursor.com>

The CI uses uv pip install (not uv sync), so the workspace root
pyproject.toml and uv.lock provided no practical value. Remove them
along with workspace-only artifacts:

- Root pyproject.toml (workspace definition, cross-package conflicts)
- uv.lock and its .gitattributes / .pre-commit-config.yaml exclusions
- { workspace = true } source mappings in cuda_core and cuda_bindings
- cuda-pathfinder from cuda_core build-system.requires (was only needed
  for the workspace resolver)

Per-package [tool.uv] conflicts (e.g. cu12 vs cu13 extras) are retained
in their respective pyproject.toml files.

Co-authored-by: Cursor <cursoragent@cursor.com>

…python

These files had incidental changes (whitespace, quoting style,
setuptools_scm config) that are outside the scope of the uv migration.
Copyright year auto-updated by pre-commit hook.

Co-authored-by: Cursor <cursoragent@cursor.com>